BBS Toolkit/BBS Toolkit.iso/wildcat/w3euti22.zip/UTI.DOC

Text File | 1992-08-06 | 20KB | 520 lines

┌───────────────────────────────────────────────┐
│ WC3 Enhanced UTIs        v2.2        8-06-92  │
└───────────────────────────────────────────────┘


What They Do
------------

UTIs (Universal Text Interface) are a group of programs that allow
the PC Relay and MegaMail door programs to interface with a BBS.
There are many different UTI programs available and each works with
a specific BBS program.

UTI programs directly access the BBS database files and perform
functions such as message imports and exports, listing available
conferences and updating last-read pointers.  Thanks to the UTI
standard interface, PC Relay can be used with many different BBS
programs.

These UTIs are designed for use with WildCat versions 3.0x to 3.5x.
They will automatically detect which version you are using and
build the message databases accordingly.


Features
--------

1.   The UTI programs will work properly in a multi-node
     environment.  These two features have been added to achieve
     multi-node compatibility:

     A.   All imported messages are marked internally with a UTI
          code.  This code identifies the message as coming from
          the UTIs.  In multi-network situations, the code also
          identifies which network the message came from.  Imported
          messages will not be exported to the same network.

     B.   The UTIs keep their own high message numbers.  If a
          message is entered online and the PC Relay software
          misses it, the UTIs will detect it and adjust the next
          export accordingly.  PC Relay and communication errors
          are taken into account and will not confuse the UTI's
          high message count.

2.   Imported text files "<<*.IMP" are exported along with outgoing
     messages just like regular text.  Each time an *.IMP file is
     exported, a message will be logged to the UTI.LOG file.

3.   Input and output files are processed as binary files instead
     of text files.  Text files are limited in that an End-of-File
     mark (ASCII 26) within a message would cause an import to end
     prematurely, sometimes causing errors and often losing
     messages.  When an end-of-file mark is detected in the middle
     of a packet, a message will be logged to the UTI.LOG file.
4.   Extra spaces at the end of a line are skipped during imports
     and exports.  The blank lines surrounding the PC Relay
     taglines often have 30-40 extraneous spaces.  By eliminating
     these wasted characters, your MSGxxx.DAT files will be
     approximately 5% smaller.

5.   Using a combination of file buffers, smart file locking and
     batch processing, the Enhanced WC3 UTIs are approximately 11-
     200% faster than earlier WildCat UTIs.  See the SUMMARY.UTI
     file for speed comparisons.


Other Information
-----------------

1.   "Soft errors" such as corrupted messages and unexpected data
     will be logged to an error file and the message will be
     skipped.  Import or export will continue with the next good
     message, if any.

2.   "Hard errors" such as missing files, full disks and too many
     open files will be logged to an error file and cause the UTI
     to stop.  An error code will be passed to the calling program
     (PC Relay, MegaMail) which normally causes the calling program
     to stop.

3.   The mail waiting flag is set in both real name and alias
     conferences.

4.   Messages are limited to 150 lines of up to 79 characters per
     line.  Lower limits may be defined using the MAKEWILD program;
     If a message exceeds the conference's line limit it will be
     split into two or more parts.

     Excessive taglines sometimes make a message exceed its line
     limit.  To avoid unnecessary message splitting, a conference's
     line limit may be exceeded by up to 10 lines if there is ample
     space in the message record.  These additional lines are
     supported by WildCat and will not cause any problems.

5.   During an import, the UTIs will abide by the conference's
     maximum message limit.  If the number of messages exceeds that
     limit, the UTIs will delete excessive messages starting with
     the lowest message number until the message limit is reached.
     Messages marked with the "No Delete" flag will not be deleted.

6.   Pressing CTRL-C will signal the UTIs to stop processing at the
     next safe opportunity.  The UTIs will stop with an errorlevel,
     signalling to the calling program that it stopped abnormally.


Setup
-----

Install the parent program (PC Relay or the MegaMail Door)
according to that program's instructions.  The UTI programs can be
placed with the PC Relay program files, or in any directory that is
listed in the path.


DOS Environment Variables
-------------------------

The UTIs can use three optional environment variables.  DOS
environment variables are defined using the SET command.

WCHOME :  This variable is optional and contains the path to the
          main WildCat directory.  An example is:

               SET WCHOME=C:\WC30

          If this variable is not defined, the UTIs will search the
          path until the main WildCat directory is found.  If you
          use the WCHOME environment variable, the UTIs will take
          less time since they won't have to search for the WildCat
          directory.

WCNODEID: If you are running a multi-node BBS and do not have the
          MAKEWILD autonode option enabled, this variable must be
          set to a unique number between 1 and 250.  See the
          section on multi-node BBSs for more information.

UTINET :  With the advent of PC Relay 4.11, the UTINET variable
          will no longer function as it was designed.  PCR 4.11
          will not export messages with a PCR tagline, even if a
          conference needs to be sent to two or more networks.
          This feature is being retained for future use.

          This variable is only important if you cross two networks
          together.  If two or more PC Relay networks access the
          same message conference, you need to set this variable to
          a unique character for each conference.  For example:

          SET UTINET=A
          SET UTINET=B

          Only one character is required, and only the first
          character will be used if there is more than one.


Multi-Node BBSs
---------------

If you are running a single-line version of WildCat, the UTIs
cannot be run while the BBS is up, or when any other utility is
accessing the message databases.

In order to use the UTIs while the BBS is online, you must be
running a multi-line WildCat version and have either DOS share or
Novell defined in the Makewild program.  If the MAKEWILD autonode
option is enabled, the UTIs will determine the proper node ID to
use.  If you are not using the autonode feature, the environment
variable WCNODEID must be set to a valid number between 1 and 250.

Use the following command:

     SET WCNODEID=3

using 3 or whichever node ID you wish to use.  This node ID must
not be duplicated.  No other BBS node or program using this node ID
may be running while the UTIs are accessing the message databases.


Renumbering the Databases
-------------------------

You must be careful when renumbering the databases.  Before you
renumber, make sure that all messages have been exported.  The best
method is to:

     1.  Take all BBS nodes down.
     2.  Run the PC Relay export program.

     You may renumber your conferences now, or wait until you
     import new messages.

Since the UTIs keep their own high message numbers, you must run
the UTIRESET program in addition to the PC Relay RESET program.
The UTIRESET program must be run in the directory where you run
your imports and exports.

If you use the UTINET environment variable, UTIRESET must be run
for each UTINET network.


Error Log File
--------------

The UTIs will record error messages to the file UTI.LOG in the
current directory.  Other events will also be logged, including:

     1.   Messages split into two or more parts.
     2.   Messages skipped due to errors.
     3.   *.IMP text files exported as part of a message.
     4.   New, non-exported messages detected during an import.
     5.   End-of-file marks detected in the middle of an import
          packet.  This is only for informational purposes; EOF
          marks have no effect on the enhanced UTIs.


Program Descriptions
--------------------
The input and output files are standard text files and follow the
UTI v2.1 specifications.  The UTI format is designed and controlled
by Kip Compton; requests for additional UTI format information
should be addressed to him.


UTIEXPRT

Exports messages from the specified conference starting with the
message number in parameter #2.  At this time, WildCat does not
have a no-echo option, so all messages will be exported.

The exception is when the /NETWORK parameter is specified.  When in
Network mode, messages that were imported from the same network ID
will not be exported.  The UTINET environment variable can be used
to change network Ids, or the default ID "0" will be used.

Network mode also enables the multi-node features.  UTIEXPRT keeps
track of its own high message numbers in the UTINETx.DAT file,
where "x" is the UTINET environment variable.  These separate high
message numbers ensure that all appropriate messages will be
exported to the network.

     Parameter 1 -  Conference number.
     Parameter 2 -  First message number to export.
     Parameter 3 -  Full path and file name of the output file.
     Parameter 4 -  /NETWORK (optional)


UTIIMPRT

Imports new messages from the input file into the specified
conference.  In Network mode, it internally marks each message with
a network code which will prevent the message from being exported
to the same network.

PC Relay pre-assigns each message a number before calling the
UTIIMPRT program.  Unless PC Relay is told otherwise, it assumes
that these message numbers will stay the same when imported into
the message conference.  If the first message number in the input
file is different than the message number used on the BBS, then the
difference is written to the adjustment file (parameter 3).

PC Relay uses the adjustment file to keep its reference numbers
accurate, however the numbers may not be accurate when:

     1.   New messages are added to the BBS while an import is in
          progress.
     2.   Invalid or corrupted messages are skipped.
     3.   Long messages are split into two or more parts.


The UTIs can tell PC Relay to adjust all the reference numbers in
an import, but there is no way to change just a few of them.
WildCat limits messages to a maximum of 12000 bytes.  The internal
WC editors are more restrictive:  When used to create a message,
the limit is 150 lines of 72 characters each, however, the editors
will allow you to safely edit an existing message of up to 164
lines of 72 characters each.  This allows full sized messages (150
lines from the source BBS) to be imported even after many taglines
have been added.

     Parameter 1 -  Conference number.
     Parameter 2 -  Full path and file name of the input file.
     Parameter 3 -  Full path and file name of the message number
                    adjustment file.  (Optional)
     Parameter 3 -  /NETWORK  (Optional)
          or   4


UTIHIGH

Reads the conference status record and writes the high message
number to the output file.

     Parameter 1 -  Conference number.
     Parameter 2 -  Full path and file name of the output file.


UTILIST

Creates a list of available conferences with their descriptions.
This list is used in the PC Relay CONFIG program and in the
MegaMail door.

     Parameter 1 -  Full path and file name of the output file.


UTIVER

Writes the UTI version number to the output file.  A second line
identifies the UTI author and/or program name.

     Parameter 1 -  Full path and file name of the output file.


UTILSTRD  (MegaMail only)

Depending on the first parameter, this program will either READ the
specified user's last read message numbers or WRITE (update) the
last read message numbers.  Output from this program will be
matched against output from UTILIST to determine which conferences
the user may access and his/her last read pointer.

     Parameter 1 -  READ or WRITE
     Parameter 2 -  Full path and file name of the input or output
                    file.
     Parameter 3 -  The user's first, middle, last name, etc.

UTIDOOR   (MegaMail only)

Creates a small door information file for use by the MegaMail door.
This program reads the DOOR.SYS file and creates the output file,
which should be UTIDOOR.TXT.

     Parameter 1 -  Full path and file name of the output file.


UTIRFLAG  (MegaMail only)

Clears a user's mail-waiting flag for a specified range of
messages.  After a user downloads messages using the MegaMail door,
this program is called to clear the mail-waiting flags.

     Parameter 1 -  Conference number.
     Parameter 2 -  Starting message number.
     Parameter 3 -  Ending message number.
     Parameter 4 -  The user's first, middle, last name, etc.


UTIRESET

This program is unique to the Enhanced UTIs; it resets the high
message numbers in the UTINETx.DAT file.  This should be run when
the message conferences are renumbered and whenever the PC Relay
"RESET" program is run.


Registration
------------

The Enhanced WC3 UTI programs are distributed as shareware.
Shareware software allows you to try before you buy, thus you never
need to pay for a shareware program that does not meet your needs.

You may use these UTIs for 30 days at no charge, allowing you a
chance to see if they meet your needs.  If you keep using them
after 30 days, you must register the software by sending in the
registration form and paying the registration fee of $20 (US).
Registered DupMsg users are entitled to a $5 discount.

Registration entitles the purchaser to use the UTIs on one BBS
system.  A BBS system is defined as either a single computer
system, or a network system where multiple computers are connected
by direct cable to the same network server.

Even after you register these UTIs, your satisfaction is
guaranteed.  If within 30 days after registering you decide that
you no longer wish to use the programs, simply write a letter to
the author requesting a refund and your registration fee will be
refunded.  Only the registration fee will be refunded, not the cost
of diskettes that may have been ordered.

Support
-------

The author can be reached via the WildNet and RelayNet mail
networks, as well as the MSI WildCat conference.  Please address
messages to Jim Metzler.

Registration fees and requests for additional information should be
addressed to:

     Jim Metzler
     WPI Box 188
     100 Institute Road
     Worcester, MA 01609

     Voice: [phone]
     BBS:   [phone]


Warranty Disclosure
-------------------

Normally, software distributed through bulletin boards systems or
shared from one user to another does not carry a warranty, mainly
because the author does not have control over the product and the
program can be modified either intentionally or accidentally
without the author's knowledge.

Recognizing this, these UTI programs carry either no warranty or a
limited warranty depending on the distribution method.

LIMITED WARRANTY:

     This applies only when the program is received directly from
     the author on diskette, or when it is received in the original
     ARJ archive, complete with a valid Security Envelope.  The ARJ
     Security Envelope must read "ARJ archive created by James W.
     Metzler R#0301".  The user must keep the diskette or original
     ARJ archive as proof of this warranty.

   - What is covered:  The UTIs program will perform substantially
     as described in this document.  In addition, while the program
     may contain minor bugs or errors, it is warranted to be free
     of major defects for a period of six months.  Diskettes
     received from the author are guaranteed to be free or defects
     for a period of six months from date of receipt.

   - What is not covered:  The author will not be liable for
     incidental and/or consequential damages, including injury to
     property, interruption of service, loss of business and/or
     anticipated profits, or other consequential damages that may
     result from use, malfunction or failure of the programs, or
     from errors or omissions in the documentation.  Some states do
     not allow the exclusion or limitation of incidental or
     consequential damages, so the above limitation may not apply
     to you.

     Any attempt to modify the UTI programs will void this warranty
     in its entirety.

   - If there is a problem:  Within 60 days of notification that a
     major defect exists, the author, at his discretion, will
     either fix the program and forward the replacement at no cost
     to the registered user, or will refund the registration fee.

     Defective diskettes will be replaced within 60 days at no cost
     to the purchaser.

   - How to get service:  Send a written letter to the author
     detailing the type of problem and symptoms experienced.
     Include your name, address, voice phone number and
     registration number and any additional information that you
     believe may be useful, such as any TSRs and disk cache
     programs in use.

     The author may contact you by voice or written letter for more
     information to help in tracking down the problem.


NO WARRANTY:

     If you did not receive the UTI programs directly from the
     author, or in its original ARJ archive with a genuine Security
     Envelope (see above), then there is a possibility that the
     programs and/or documentation have been modified, or that the
     program is not the author's work.  The author makes no
     warranty of any kind, express or implied, including any
     warranties of fitness and/or merchantability if the program
     was received from other sources.

     The author will not be liable for any damages, whether direct,
     indirect, special or consequential arising from a failure of
     this program to operate in the manner desired by the user.
     The author will not be liable for any damage to data or
     property which may be caused directly or indirectly by use of
     the program.

When trying new software, always backup any and all important files
on your system.


Special Thanks
--------------

Special thanks to Peter Anderson, Ralph Maya, Ryan Cramer, Bob
Allman, Bill Anton and Mike Callaghan for their help ßeta testing
these programs.  Their assistance has been invaluable in the
development of these programs.


Copyright
---------

These UTI programs are:
Copyright (c) 1992, James W. Metzler, All Rights Reserved.


About the Author
----------------

Jim Metzler grew up on the IBM side of Silicon Valley, within
blocks of the Santa Teresa IBM plant.  Jim is an Eagle Scout and
Vigil member of the Order of the Arrow; one of his first computer
projects was computerizing the membership records for the Santa
Clara County OA Lodge (Miwok 439) in the early 1980's.

After attending college part-time, Jim joined the Navy as a Data
Processing Technician and spent 3 years in and around Japan,
stationed onboard the USS Blue Ridge (LCC-19), Seventh Fleet
Flagship.  Jim operated, then later managed two Wang mini-computers
that served Seventh Fleet staff and was responsible for the Ship's
ADP Security program.  For the last two years, Jim served at the
White House Communications Agency in Washington, DC, providing
computer support to the President and his staff both in town and on
the road.

Just recently out of the Navy, Jim is continuing his college
studies at Worcester Polytechnic Institute in Worcester, MA.

-----------------------------------------------------------------